#
#COMPILE             DELETE            EXIT        HELP
#LIBRARY             LINK              OPTIONS     PACKAGE_SPECS
#PROGRAM_LIBRARY     QUIT              RUN         SET_LIBRARY       
#SOURCE_INSTRUMENT   SYSTEM_COMMANDS
#
*************
$?\?\N/A\WIS_DEBUG Options are:  (UPPER CASE indicates minimum required input)
+
+  Library Management
+    SEt_library(PROGRAM_LIBRARY); --> Set current program library
+    Delete(UNIT_NAME);            --> Delete a unit from program lib
+
+  Execution Control
+    SOurce_instrument;            --> Instrument an Ada source file
+    Compile(SOURCE_FILE);         --> Compile an instrumented comp unit
+    LINk(COMPILATION_UNIT);       --> Link an instrumented program
+    Run(COMPILATION_UNIT);        --> Run the Debugger with an instr pgm
+    QUit;  --> or EXit;           --> Quit WIS_DEBUG and Exit to the system
+
+  SYstem_command(COMMAND);        --> Execute a system command
+
+  Help                            --> Help for commands and features
*************
\COMPILE\C\None\Compile an instrumented Ada compilation unit
?
+Syntax:  COMPILE(SOURCE_FILE);   --> or C(SOURCE_FILE
+         Where SOURCE_FILE is the name of an Ada compilation unit.
+
+Invokes the Ada Compiler to compile the specified Ada source file from
+within the WIS_DEBUG Shell.
+
+After a unit has been instrumented by the Source Instrumenter it must be
+compiled using your Ada compiler.  If you did not select  the  automatic
+compilation option after source instrumentation then  you  may  use  the
+COMPILE command to avoid exiting the WIS_DEBUG Shell.
E
+  1) COMPILE(TEST.INS);
+
+  2) COMPILE(TEST.INS)
+
+  3) COMPILE(TEST.INS
*************
\DELETE\D\None\Delete a unit from the Current Program Library
?
+Syntax:  DELETE(UNIT_NAME);     --> or D(UNIT_NAME
+
+The Source Instrumenter creates numerous files in the Current  Program
+Library that are used during execution of the Symbolic  Debugger  with
+the instrumented program.   When an  instrumented  program  unit is no
+longer needed it must be deleted from the program  library  using  the
+DELETE command.
+
+No file extension should be specified.  Only files that are created by
+by the Source Instrumenter in the Current Program Library are deleted.
+The user must delete unwanted  files that are  created in the  working
+directory when the Source Instrumenter is executed.
E
+  1) DELETE(OLD_PROGRAM);
+
+  2) DEL(OLD_PROGRAM
+
+  3) D(OLD_PROGRAM
*************
$EXIT\E\None\Command:  Quit WIS_DEBUG and EXIT to the system
+Abbreviation:   EX     --> 2 chars to avoid accidental entry
+Syntax:         EXIT;  --> or EX
?
+The EXIT command is functionally equivalent the QUIT command.  Some people
+prefer EXIT and some prefer QUIT.  Both terminate the  WIS_DEBUG Shell and
+return the user to the system command level.
E
+  1)  >> EXIT;      3)  >> EXI;         5)  >> EX;
+
+  2)  >> EXIT       4)  >> EXI          6)  >> EX
*************
\HELP\H\None\Display information about WIS_DEBUG Shell commands and features
?
+Syntax:  HELP;            --> or H
+         HELP(topic);     --> or H(topic
+
+Displays information about WIS_DEBUG  Shell  commands  and  features.   The
+HELP command may be entered at any  time  WIS_DEBUG is in  "command"  mode.
+"Topic" may be abbreviated.  If no "topic" is specified or  if  an  invalid
+"topic" is specified then a menu of all available HELP topics is displayed.
+If "topic" is ambiguous then a list  possible  intended  topics  and  their
+minimum abbreviations is displayed.
+
+Help files may be modified or expanded by the user to add project or system
+specific information, new terminal configurations,  information about bugs,
+or any other topic.  The format of the  help  file  and  information  about
+adding new topics may be found in the WIS_DEBUG User's Guide.
+
E
+  1) HELP;       --> Will display a menu of all available HELP topics
+
+  2) HELP(HELP); --> Will display information about the HELP command
+
+  3) HELP(RUN    --> Will display information about the RUN command
*************
\LIBRARY\LIB\None\Set the current program library
?
+Syntax:  LIBRARY(LIBRARY_NAME);   --> or LIB(LIBRARY_NAME
+
+         where LIBRARY_NAME is the complete path name of the directory
+         to be used as the WIS_DEBUG Current Program Library
+
+The LIBRARY command is functionally equivalent to the SET_LIBRARY command.
E
+  1) LIBRARY( DRA0:[USER.BUBBA_SMITH.PGMLIB] );
+
+     A logical device identifier (DRA0:) is required if the Program
+     Library is not located on the current default logical device.
+
+  2) LIB( [USER.NOSC.PGMLIB] )
+
+     The full path name of the directory is required if the Program 
+     Library is not in the current default working directory.
+
+  3) LIB( [.PGMLIB]
+
+     The Program Library is set to the PGMLIB subdirectory of the
+     current working directory.
*************
\LINK\LIN\None\Link an instrumented program
?
+Syntax:  LINK(COMPILATION_UNIT);   --> or LIN(COMPILATION_UNIT
+
+Invokes the linker to link an instrumented compilation unit from within
+the WIS_DEBUG  Shell.   The executeable  load module is created in  the
+user's current working directory.
E
+  1) LINK(TEST);
+
+  2) LINK(TEST)
+
+  3) LIN(TEST
*************
$OPTIONS\O\None\WIS_DEBUG Command Options are:
+
+  COMPILE           --> Compile an instrumented Ada compilation unit
+  DELETE            --> Delete a unit from the Current Program Library
+  EXIT              --> Quit WIS_DEBUG and EXIT to the system
+  HELP              --> Display information about commands and features
+  LIBRARY           --> Set the Current Program Library
+  LINK              --> Link an instrumented program
+  QUIT              --> Quit WIS_DEBUG and exit to the system
+  RUN               --> Run the Debugger with an instrumented program
+  SET_LIBRARY       --> Set the Current Program Library
+  SOURCE_INSTRUMENT --> Instrument an Ada source file
+  SYSTEM_COMMAND    --> Execute a system command
+
+WIS_DEBUG command options may be displayed at any time by entering "?".
+
+For more information about a particular option enter HELP( <option_name> );
*************
$PACKAGE_SPECS\PA\None\Instrumenting Ada Package Specifications
+
+     When  the  source  file  you are  instrumenting  includes  a  package
+specification, the source instrumenter will ask you if you want to include
+the package spcecification in your instrumented source.
+
+     If  your package specification includes a generic declaration and you
+want  to  instrument the generic body,  then you must answer YES  to  this
+question.    Otherwise,   instrumenting   will  not  alter  your   package
+specification  and  recompiling  your package  specification  may  not  be
+required.
+
+     The   source  instrumenter  will  create  a  package  which  has  the
+procedures  necessary  to trace any types and variables declared  in  your
+package  specification.   The source instrumenter's package will WITH  and
+USE your package.   Therefore, your package specification must be compiled
+prior to compiling the source instrumenter's package.
?
+     If you need to compile or recompile your package spcecification,  you
+may  have  it  included  in the same file  as  the  source  instrumenter's
+package.   Then  when  you  compile the  instrumented  source  file,  both
+packages will be compiled.   You will have to recompile your package  body
+and  all dependent units as usual.   If you do not want to recompile  your
+package specification,  answer NO to the question.  You will still need to
+compile  the  instrumented  source  file,  but your package  will  not  be
+affected.
*************
$PROGRAM_LIBRARY\PR\None\The WIS_DEBUG Program Library Consists of:
+
+   1) The Base Program Library
+
+   2) A Current Program Library
?
+The Base Program Library is created at the time  WIS_DEBUG is  installed
+and contains static non-transient files that are common to all  users of
+the debugger, such as the Terminal Capabilities File and help files.
+
+The Current Program Library contains dynamic information that is created
+and used by the Source Instrumenter and by the debugger during execution
+of the instrumented program.  The Current Program Library must be set at
+run time by using the SET_LIBRARY command.
*************
$QUIT\Q\None\Command: QUIT WIS_DEBUG and exit to the system
+Abbreviation:   QU     --> 2 chars to avoid accidental entry
+Syntax:         QUIT;  --> or QU
?
+The QUIT command is functionally equivalent the EXIT command.  Some people
+prefer QUIT and some prefer EXIT.  Both terminate the WIS_DEBUG  Shell and
+return the user to the system command level.
E
+  1)  >> QUIT;      3)  >> QUI;         5)  >> QU;
+
+  2)  >> QUIT       4)  >> QUI          6)  >> QU
*************
\RUN\R\None\Run the Symbolic Debugger with an instrumented program
?
+Syntax:  RUN(PROGRAM)  --> or R(PROGRAM
+
+Runs the Symbolic Debugger with an instrumented program from within
+the WIS_DEBUG Shell.   The PROGRAM  must have already been compiled
+and linked.
E
+  1) RUN(TEST);
+
+  2) RUN(TEST
+
+  3) R(TEST
*************
\SET_LIBRARY\SE\None\Set the current program library
?
+Syntax:  SET_LIBRARY(LIBRARY_NAME);   --> or SET_L(LIBRARY_NAME
+
+         where LIBRARY_NAME is the complete path name of the directory
+         to be used as the WIS_DEBUG Current Program Library
+
+The SET_LIBRARY command is functionally equivalent to the LIBRARY command.
E
+  1) SET_LIBRARY( DRA0:[USER.BUBBA_SMITH.PGMLIB] );
+
+     A logical device identifier (DRA0:) is required if the Program
+     Library is not located on the current default logical device.
+
+  2) SET_LIB( [USER.GEORGE_BURNS.PGMLIB] )
+
+     The full path name of the directory is required if the Program 
+     Library is not in the current default working directory.
+
+  3) SE( [.PGMLIB]
+
+     The Program Library is set to the PGMLIB subdirectory of the
+     current working directory.
*************
\SOURCE_INSTRUMENT\SO\None\Instrument an Ada source file
?
+Syntax:  SOURCE_INSTRUMENT;
+         SOURCE_INSTRUMENT(INPUT_FILE,
+                           SOURCE_LISTING_FILE,
+                           INSTRUMENTED_SOURCE_FILE);
?
+Instruments an Ada source  program to insert  "hooks"  to the Symbolic
+Debugger.  If input and output file names are not specified  then  the
+user will be prompted  for  their  names by the  Source  Instrumenter.
+Only the input file name must be specified.   If no output file  names
+are specified then default names <input_file>.LST and <input_file>.INS
+will be used.
E
+  1)  SOURCE_INSTRUMENT(TEST.ADA, TEST.LIS, TEST.SI); <cr>
+
+      source_file = TEST.ADA
+      source_listing = TEST.LIS
+      instrumented_source = TEST.SI
E
+  2)  SOURCE_INSTRUMENT <cr>
+
+      Enter Source_File => TEST.ADA <cr>
+      Enter Source_Listing => TEST.LIS <cr>
+      Enter Instrumented_Source_File => TEST.SI <cr>
+
+      source_file = TEST.ADA
+      source_listing = TEST.LIS
+      instrumented_source = TEST.SI
E
+  3)  SO <cr>
+
+      Enter Source_File => TEST.ADA <cr>
+      Enter Source_Listing => <cr>
+      Enter Instrumented_Source_File => <cr>
+
+      source_file = TEST.ADA
+      source_listing = TEST.LST
+      instrumented_source = TEST.INS
*************
\SYSTEM_COMMAND\SY\None\Execute a system command from the WIS_DEBUG Shell
?
+Syntax:  SYSTEM_COMMAND(COMMAND);
+
+Executes a system command or another  program from  within the  WIS_DEBUG
+Shell.   May be  used  for  editing  source  programs,  file  management,
+submitting jobs to a batch stream,  printing Source Instrumenter listings
+for use during a debugging session, etc.
+
+When spawned process is completed, any changes that have been made to the
+environment will be restored to their state prior  to  execution  of  the
+SYSTEM_COMMAND.
E
+  1)  SYSTEM_COMMAND( DIR/DATE );
+
+  2)  SYSTEM_COMMAND( EDIT TEST.ADA
+
+  3)  SY( PRINT TEST.LST
